Dynomotion

Group: DynoMotion Message: 13793 From: engnerdan Date: 10/10/2016
Subject: Possible Bug
I am not sure if this is a bug or something up with the settings for my machine. Last night while running a helical interpolated bore on a part the programmed feed-rate was never really achieved.  I have had this happen on a couple parts in the past and forgot to bring it up. Attached is the G-Code file.

Here is a video if it running
https://youtu.be/Fc_W8VWrSI8

Second Video
https://youtu.be/e1Oua-x0kZY

-Dan


   @@attachment@@
Group: DynoMotion Message: 13815 From: Tom Kerekes Date: 10/10/2016
Subject: Re: Possible Bug [1 Attachment]

Hi Dan,

I think the Feed Rate is actually working correctly.  The problem is with the status display.  When requested by KMotionCNC KFLOP basically samples the XYZ positions and Timestamps the exact time they were sampled.  These Time/Positions are requested about 10X per second by KMotionCNC.  KMotionCNC displays the Feed Rate as delta Position/delta Time between the last two sampled points.  This represents the average speed over the last 0.1 seconds to travel along a straight line between the two points.  Your Job basically consists of small circles drawn 6X per second.  The result is poor.

I suppose the better solution would be to somehow capture the last instantaneous velocities.

Do you think this is a big issue for you?

Regards

TK


On 10/10/2016 6:01 AM, engnerdan@... [DynoMotion] wrote:
 

I am not sure if this is a bug or something up with the settings for my machine. Last night while running a helical interpolated bore on a part the programmed feed-rate was never really achieved.  I have had this happen on a couple parts in the past and forgot to bring it up. Attached is the G-Code file.

Here is a video if it running
https://youtu.be/Fc_W8VWrSI8

Second Video
https://youtu.be/e1Oua-x0kZY

-Dan
Group: DynoMotion Message: 13819 From: Dan W Date: 10/11/2016
Subject: Re: Possible Bug
If it's just a display issue, it is not a big deal to me and would no need immediate attention.  

But if you listen to the cut in the second video you can hear the cut slow down.  

I think I have another video clip of the same type of cut in a solid block and it looks to slow.  

Either way this is not a huge problem for me right now, my program just runs slow for one part. 

Dan



Sent via the Samsung Galaxy S®6 active, an AT&T 4G LTE smartphone



Group: DynoMotion Message: 13823 From: Tom Kerekes Date: 10/11/2016
Subject: Re: Possible Bug
Hi Dan,

I can't really hear the slow down.

I couldn't resist adding an instantaneous feedrate DRO using the KMotionCNC Screen Editor.

See the video:

https://youtu.be/w-bKvqXCd0Q

I've also attached the Screen Script for that Screen and the C Program. 

(scr file renamed to .txt as Yahoo Groups doesn't seem to like .scr files)

Regards
TK



On 10/11/2016 8:31 AM, Dan W engnerdan@... [DynoMotion] wrote:
 
If it's just a display issue, it is not a big deal to me and would no need immediate attention.  

But if you listen to the cut in the second video you can hear the cut slow down.  

I think I have another video clip of the same type of cut in a solid block and it looks to slow.  

Either way this is not a huge problem for me right now, my program just runs slow for one part. 

Dan



Sent via the Samsung Galaxy S®6 active, an AT&T 4G LTE smartphone



Group: DynoMotion Message: 13827 From: Dan W Date: 10/11/2016
Subject: Re: Possible Bug [2 Attachments]
Thanks I will have to add that and see what I am getting.  

During the video your machine was still running up in the 20's for IPM.  My machine is only getting about 9 IPM. 

-Dan



Sent via the Samsung Galaxy S®6 active, an AT&T 4G LTE smartphone